Fixed malformed response from bad ARCOUNT #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
_authority and _additional are never filled with data but at response, the corresponding counters are not 0 but contain the counters from the request which will produce a malformed response
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
_authority and _additional are never filled with data but at response, the corresponding counters are not 0 but contain the counters from the request which will produce a malformed response.
For example, running
dig @127.0.0.1 facebook.com Awould show a warning like this:;; Warning: Message parser reports malformed message packet.Caused by the fact that at request the ARCOUNT is 1, but at response, there's no Additional Response entries, but the counter is set to 1.